-
Notifications
You must be signed in to change notification settings - Fork 39
Remove Service Override from aws.lambda spans
#666
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
astuyve
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this can ship. Many assumptions are made in the backend based on this
What part exactly is blocking? Is it changing the service name from Or is it respecting the DD_SERVICE env var specifically for lambda spans? That isn't really changing any behavior because the rust extension already does that. This change simply performs that renaming earlier in the life of the trace so that base_service is not on the tracer leading to indications of a service override on the UI even though the base_service and actual service are the same. |
|
Reminder - Use this PR to collapse cold start to use Boolean values |
joeyzhao2018
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
What does this PR do?
Change the lambda span service name priority:
DD_SERVICEaws.lambdaAlso changes
cold_startvalues to true/falseAdds
DD_TRACE_AWS_SERVICE_REPRESENTATION_ENABLEDto allow disabling of feature when set to false. Default is true.Motivation
Removes service overrides for
aws.lambdaspanTesting Guidelines
Additional Notes
Types of Changes
Check all that apply